Method for assigning a priority mechanism to at least one group of TLV-objects

ABSTRACT

Method for assigning a priority mechanism to a least one group of TLV-objects (TLVO 1 -TLVO 3 ) for data exchange between a transmitting and receiving entity, for storing data on, and/or for reading data from a storage medium by assigning a structure (ST) for TLV-objects in the transmitting and receiving entity; and/or on the storage medium.

BACKGROUND OF THE INVENTION

The standardization body 3GPP TSG SA1, which is responsible for thedefinition of general MMS service aspects (see 3GPP TS 22.140,Multimedia Messaging Service (MMS); Service Aspects; Stage 1 (Release5)), has approved new requirements for (automatic) bearer selection inMMS (Multimedia Messaging Service). According to these requirements, anMMS-capable UE (=User Equipment: e.g., a mobile phone) shall be able toautomatically select a bearer from a list of different sets of Interfaceto Core Network and Bearer parameters stored in the USIM (UMTSSubscriber Identity Module) based on their order of precedence. Whenautomatic selection of bearers is disabled, the user shall be able toselect a bearer manually from the Interface to Core Network and Bearerparameters. Furthermore, it is also desirable that the switch to a lesspreferred bearer, in case the most preferred is not available, takesplace without any user intervention. Network operators and users willbenefit from the usage of the most suitable bearer for the delivery andsubmission of Multimedia Messages. Currently, in the 3GPP USIMspecification TS 31.102, there is no way to express any order ofprecedence with the storage of Interface to Core Network and Bearerparameters and, thus, the new standardization requirements cannot bemet.

The present invention aims to bring a solution to the above-describedproblem. It preferably defines two alternative, advantageous mechanismsto prioritize a list of TLV objects, and two corresponding mechanismsfor automatic bearer selection from the MMS Interface to Core Networkand Bearer parameters based on their order of precedence.

Nowadays, in mobile networks like GSM (Global System for MobileCommunications), SMS (Short message Service) is used to send and receiveshort messages between mobile terminals. Currently, a new messagingservice, the so-called MMS (Multimedia Messaging Service) is beingstandardized. Contrary to SMS, MMS messages may contain multimediaelements such as, for example, text, image, audio or video.

MMS is a peer-to-peer messaging service between two MMS User Agentswhich are both connected to an MMS Relay/Server. The User Agent resideseither on a mobile phone, such as a UMTS-UE (User Equipment) or a GSM-MS(Mobile Station), on an external device, such as a notebook/laptop,connected to a mobile phone, or even on a PC. It is preferable anapplication layer function that provides the user with the ability toview, compose and handle the Multimedia Messages (=MMs); for example,the submitting and receiving of MMs. The MMS Relay/Server is a networkentity responsible for the storage and handling of incoming and outgoingmessages and for the transfer of messages between different messagingsystems. In general terms, there is a data exchange between such atransmitting and receiving entity.

Mobile communication services such as the 2^(nd) generation (e.g., GSM(Global System for Mobile Communications)) and the 3^(rd) generation,(e.g., UMTS (Universal Mobile Telecommunication Service) preferably usewell-defined smart cards in addition to mobile phones. Plugged into amobile phone, these smart cards enable a user to use the mobilecommunication service he/she has subscribed to. Moreover, userpreferences and settings as well as a user's personal information can bestored on such smart cards. In GSM these cards are called SIM(Subscriber Identity Module). In UMTS one distinguishes between thephysical card which is called UICC (Universal IC Card; IC: IntegratedCircuit) and its logical functionality, the USIM (UMTS SubscriberIdentity Module).

An Elementary File for MMS Connectivity Parameters (=EFMMSCP) is definedon the USIM. This EF (Elementary File) contains values for MultimediaMessaging Connectivity Parameters, which can be used by the ME for userassistance in preparation of connecting to the network for the MMSpurpose. The EFMMSCP is present, when the MMS service in the USIMservice table is “available.” This EFMMSCP is shown in FIG. 1.

The EFMMSCP is an transparent file (for example, on a storage mediumlike a smart card), where the MMS connectivity parameters are stored insequential order. To make searching and reading out of the parameterseasier, the parameters are stored by making use of the so-called,constructed TLV (Tag, Length, Value) object structure. The MMSConnectivity Parameters consist of MMS implementation, which indicatesthe used implementation (e.g., WAP), the MMS Relay/Server address, a setof Interface to Core Network and Bearer Information including accesspoint for the core network (e.g., GGSN) and required bearer informationelements (e.g., Bearer, Address, Type of address, Speed, Call type,Authentication type, Authentication id, Authentication password) and aset of Gateway Information (e.g., Address, Type of address, Port,Service, Authentication type, Authentication id and Authenticationpassword). All this information is coded according to the guidelineprovided in 3GPP TS 23.140 (see 3GPP TS 23.140, Multimedia MessagingService (MMS); Functional description; stage 2 (Release 5)).

SUMMARY OF THE INVENTION

In an embodiment of the present invention, a method is provided forassigning the priority mechanism to at least one group of TLV-objectsfor data exchange between the transmitting and receiving entity, forstoring data on, and/or for reading data from a storage medium byassigning a priority structure for the TLV-objects in the transmittingand receiving entity and/or on the storage medium.

In an embodiment of the method, the priority structure is expressed bythe order of precedence of the TLV-objects.

In an embodiment of the method, the priority structure is defined withinthe field value of at least one TLV-object.

In an embodiment of the method, the TLV-objects, for which the prioritystructure was assigned, are different sets of MMS connectivityinformation.

In an embodiment of the method, the TLV-objects for which the prioritystructure was assigned, are different sets of interface to core networkand barrier bearer information within the value field of at least oneinterface to core network and bearer TLV-object.

In an embodiment of the method, the priority structure for theTLV-objects is assigned by sequential numbering of the tag values of theTLV-objects.

In an embodiment of the method, the tag values are applied in such awaythat they are unique in a number of tags of the TLV-objects.

In an embodiment of the method, the TLV-object with the highest priorityis of mandatory status.

In an embodiment of the method, the transmitting and/or receiving entityis mobile equipment.

In an embodiment of the method, the selection of bearers for MMS isautomatically performed by the mobile equipment based on the assignedpriority structure of the TLV-objects.

In an embodiment of the method, the storage medium is a smart card,particularly a SIM, UICC, USIM, WWIM, R-UIM or DIM.

In an embodiment of the method, the storage medium is plugged into userequipment.

Additional features and advantages of the present invention aredescribed in, and will be apparent from, the following DetailedDescription of the Invention and the Figures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1, consisting of parts 1A and 1B illustrates the storage of MMSconnectivity parameters in EFMMSCP as defined in 3GPP TS 31.102 V5.0.0(Release 5) Characteristics of the USIM Application.

FIG. 2 illustrates how the order of precedence for “Interface to CoreNetwork and Bearer Information” is expressed by the order of differentsets of MMS Connectivity Information according to a first embodiment ofthe present invention,

FIG. 3, consisting of parts 3A and 3B, illustrates how the order ofprecedence for “Interface to Core Network and Bearer Information” isexpressed by the order of different sets of MMS Connectivity Informationaccording to the first embodiment of the present invention on a USIMlevel.

FIG. 4 illustrates how the order of precedence for “Interface to CoreNetwork and Bearer Information” is expressed by their order within oneset of MMS Connectivity Information according to a second embodiment ofthe present invention.

FIG. 5, consisting of parts 5A and 5B, how the order of precedence for“Interface to Core Network and Bearer Information” is expressed by theirorder within one set of MMS Connectivity Information according to thesecond embodiment of the present invention on a USIM level.

Like reference signs refer to corresponding parts and elementsthroughout FIGS. 1 through 5.

DETAILED DESCRIPTION OF THE INVENTION

According to the present invention, the following example is discussed.The mechanisms in this example allow the MMS-capable UE to automaticallyselect a bearer from the Interface to Core Network and Bearer parametersbased on their order of precedence as defined on the USIM unlessotherwise specified by the user. When automatic selection of bearers isdisabled, the user is still able to select a bearer manually from theInterface to Core Network and Bearer parameters. There are twopreferable ways to achieve this:

-   -   I) The first way to achieve automatic bearer selection is to        assign a priority mechanism to MMS Connectivity Parameters sets        (see FIG. 2). Several sets (for example, TLVO1-TLVO3 in—FIG. 2)        of MMS connectivity parameters can be stored in the EFMMSCP, set        1: 1st MMS connectivity parameters TLV11-TLV41 (tag, length,        value), set 2: 2nd MMS connectivity parameters, set 3: 3rd MMS        connectivity parameters. All the connectivity parameters sets        consist of MMS implementation, MMS Relay/Server, Interface to        Core Network and Bearer information and Gateway information. In        all these three MMS connectivity parameters sets, the MMS        Implementation, the MMS Relay/Server and the Gateway information        may be the same (MMS Implementation A, MMS Relay/Server A and        Gateway A), only the Interface to Core Network and Bearer        information differ from each other (1st MMS connectivity        parameters =>Interface to Core Network and Bearer A, 2nd MMS        connectivity parameters =>Interface to Core Network and Bearer        B, 3rd MMS connectivity parameters =>Interface to Core Network        and Bearer C). In general the order of precedence for “Interface        to Core Network and Bearer Information” is expressed,        respectively assigned by the order of different sets of MMS        connectivity Information. For assigning a priority mechanism to        at least one group of TLV-objects (for example, TLVO1-TLVO3 in        FIG. 2) for data exchange between a transmitting and receiving        entity, for storing data on, and/or for reading data from a        storage medium, a structure ST is assigned, particularly defined        for TLV-objects; for example, TLVO1-TLVO3 in the transmitting        and receiving entity, and/or on the storage medium. The priority        structure ST is preferably expressed by the order of precedence        of the TLV-objects like TLVO1-TLVO3. Thereby, such structure is        preferably defined within the value field (e.g., VAL1 in FIG. 2)        of at least one TLV-object (e.g., TLVO1). Advantageously, the        TLV-objects, for which the priority was assigned, are different        sets; e.g., TLVO1-TLVO3 of MMS connectivity information.

In case of automatic bearer selection, the MMS UA will alwaysconveniently select the MMS Connectivity Parameters set with the highestpriority; in this example the 1^(st) set of MMS connectivity parameters.When the automatic bearer selection is deactivated, the user can selectthe preferred bearer manually from the list of bearers. In the exampleaccording to FIG. 2, the user can choose between the 1^(st) set of MMSconnectivity parameters, the 2^(nd) MMS set of connectivity parametersand the 3^(rd) set of MMS connectivity parameters.

FIG. 3, by way of example, shows how different sets of MMS ConnectivityInformation can be stored on the USIM and how the order of precedencefor Interface to Core Network and Bearer Information can be expressed.Automatic bearer selection can make use of the order of the differentsets of MMS Connectivity Information as described above. FIG. 3illustrates how the order of precedence for “Interface to Core Networkand Bearer Information” is assigned, particularly expressed by the orderof different sets of MMS Connectivity Information on USIM level: Apriority mechanism is assigned to the group of MMS ConnectivityParameters TLV objects: 1^(st) MMS Connectivity Parameters TLV objects(highest priority), 2^(nd) MMS Connectivity Parameters TLV objects, . .. , n^(th) MMS Connectivity Parameters TLV objects (lowest priority).The way in which the automatic bearer selection based on the order ofprecedence for Interface to Core Network and Bearer Information works isdescribed above.

-   -   II) Another advantageous way to achieve the storage of different        sets of Interface to Core Network and Bearer Information        together with precedence information on the USIM for automatic        bearer selection is depicted in FIG. 4. The order of precedence        for Interface to Core Network and Bearer Information is        expressed by their order within one set of MMS Connectivity        Information; i.e., the priority mechanism is defined for a list        of TLV objects that are the “value” (e.g., VALF) of a TLV object        (e.g., TLVO). MMS connectivity Parameters contain MMS        implementation, MMS Relay/Server, Interface to Core Network and        Bearer information and Gateway information. The Interface to        Core Network and Bearer information TLVO may consist of several        sets of Interface to Core Network and Bearer information: 1st        Interface to Core Network and Bearer information (e.g., SE1);        2nd Interface to Core Network and Bearer information (e.g.,        SE2), . . . , nth Interface to Core Network and Bearer        information (e.g., SEn). Thus, in FIG. 4, the order of        precedence for “Interface to Core Network and Bearer        Information” is expressed by their order within one set SE of        MMS Connectivity Information. In general terms, the TLV-objects,        for which the priority was assigned, are different sets (e.g.,        SE1-Sen) of interface to core network and bearer information        within the value field (e.g., VALF) of at least one interface to        core network and bearer TLV-object.

In case of automatic bearer selection, the MMS UA will always select theMMS Connectivity Parameters set with the highest priority; in thisexample, the 1 st set of Interface to Core Network and BearerInformation. When the automatic bearer selection is deactivated, theuser can select the preferred bearer manually from the list of bearers.In this example, the user can choose between the 1st set of Interface toCore Network and Bearer information, the 2nd set of Interface to CoreNetwork and Bearer information and the nth set of Interface to CoreNetwork and Bearer information.

FIG. 5 shows how different sets of Interface to Core Network and BearerInformation can be stored within one TLV object on the USIM and how theorder of precedence for Interface to Core Network and Bearer Informationcan be expressed. Automatic bearer selection can make use of the orderof the different sets of the Interface to Core Network and BearerInformation as described above. Particularly in FIG. 5, the order ofprecedence for “Interface to Core Network and Bearer Information” isexpressed by their order within one set of MMS Connectivity Informationon the USIM level. Thereby the priority structure for the TLV-objects isassigned by sequential numbering (e.g., SN) of the tag values (e.g., TV)of the TLV-objects. The tag values are applied in such a way that theyare unique within the multiple tags of the TLV-objects.

A priority mechanism is assigned within a TLV object dedicated to theInterface to Core Network and Bearer Information; namely 1^(st) MMSInterface to Core Network and Bearer Information TLV objects (highestpriority), 2^(nd) MMS Interface to Core Network and Bearer InformationTLV objects, . . . , n^(th) MMS Interface to Core network and BearerInformation TLV objects (lowest priority). The way in which theautomatic bearer selection by using the order of precedence for“Interface to Core Network and Bearer Information” work is describedabove.

For all embodiments, the TLV-object with highest priority isadvantageously of mandatory status.

The present invention provides two advantageous, alternative solutionsto store different sets of Interface to Core Network and BearerInformation on the USIM in order of precedence as required by 3GPP TSGSA1 and allows the MMS-capable UE to automatically select a bearer fromthese different sets of Interface to Core Network and Bearer parametersbased on their order of precedence unless otherwise specified by theuser. When automatic selection of bearers is disabled, the user is stillable to select a bearer manually from the sets of Interface to CoreNetwork and Bearer parameters.

An advantage of the mechanisms described herein is that the user's MMScapable terminal can be either configured either automatically (i.e.without any user interaction) with the appropriate bearer based on theorder of precedence or manually.

Another advantage is that the mechanisms described herein areindependent of the user's particular Mobile Equipment (i.e. mobilephone) at a certain point of time. The priority for the bearer selectionmechanisms described is preferably stored on the USIM on the UICC, whichcan be plugged into Mobile Equipment (=ME) or any apparatus connected toa terminal (user equipment=mobile equipment+storage; e.g., smart card).

For this, preferably provided are:

Mechanisms for automatic and manual bearer selection from the MMSInterface to Core Network and Bearer parameters based on their order ofprecedence defined on Smart Cards:

-   a) The order of precedence for Interface to Core Network and Bearer    Information expressed by the order of different sets of MMS    Connectivity Information.    -   Definition of a priority mechanism for a group of TLV objects in        an EF (Element File) on a smart card; e.g., SIM, UICC, USIM,        WIM, R-UIM, DIM, etc.    -   Functionality of the MMS UA for handling automatic and manual        bearer selection (see example(s) of the present invention        according to FIG. 2-5).-   b) The order of precedence for Interface to Core Network and Bearer    Information is expressed by their order within one set of MMS    Connectivity Information.    -   Definition of a priority mechanism for a group of TLV objects        within one (constructed) TLV object in an EF on a smart card;        e.g., SIM, UICC, USIM, WIM, R-UIM, DIM, etc.    -   Functionality of the MMS UA for handling automatic and manual        bearer selection (see example(s) of the present invention        according to FIGS. 2-5).

Further, the mechanisms to assign priority to TLV objects as describedherein can be applied to any application that makes use of TLV objects.The mechanisms to assign priority to TLV objects also can be used forother general purposes where TLV objects are used.

Further, the automatic and manual selection mechanisms of prioritizedTLV objects as described herein are not restricted to the purpose ofstoring “Interface to Core Network and Bearer Information” on the USIM.The mechanisms can be applied to any application that makes use of TLVobjects as well. The automatic and manual selection mechanisms also canbe used for other general purposes where TLV objects are used.

Although the present invention has been described with reference tospecific embodiments, those of skill in the art will recognize thatchanges may be made thereto without departing from the spirit and scopeof the present invention as set forth in the hereafter appended claims.

The present invention particularly makes use of the followingreferences:

-   -   [1] 3GPP TS 31.102 V5.0.0 (Release 5), Characteristics of the        USIM Application    -   [2] 3GPP TS 23.140, Multimedia Messaging Service (MMS);        Functional description; stage 2(Release 5)    -   [3] W. Rankl, W. Effing, Smartcard Handbook, John Wiley & Sons,        second edition, 2000.    -   [4] 3GPP TS 22.140, Multimedia Messaging Service (MMS); Service        Aspects; Stage 1 (Release 5)

1. Multimedia Messaging Service (MMS) capable mobile equipmentcomprising: a) an elementary file containing values for a set ofMultimedia Messaging Connectivity Parameters, which can be used by theMMS capable mobile equipment for an MMS network connection; b) theelementary file being a transparent file which is present only, if aMultimedia Messaging Service is available wherein, the MMS contains atleast one set of Multimedia Messaging Connectivity Parameters; c) theset of Multimedia Messaging Connectivity Parameters being stored, bymaking use of a Tag, Length, Value (TLV) object structure, in an MMSConnectivity TLV object, including at least the following objects: anMMS Implementation TLV object indicating which implementation is usedfor the Multimedia Messaging Service, an MMS Relay/Server TLV objectcontaining the address of an associated MMS relay/server, an Interfaceto Core Network and Bearer Information TLV object to set up a bearerincluding at least: Bearer, Address, Type of address, Speed, Call type,Authentication type, Authentication id, and Authentication password, aGateway TLV object including at lest one of Address, Type of address,Port, Service, Authentication type, Authentication id, andAuthentication password; d) wherein the set of Multimedia MessagingConnectivity Parameters includes at least one Interface to Core Networkand Bearer information TLV object, one MMS Implementation TLV object,one MMS Relay/Server TLV object, and one Gateway TLV object; and e)wherein an order of the at least one Interface to Core Network andBearer information TLV object in the MMS Connectivity TLV object definesthe priority of Interface to Core Network and Bearer information, with afirst Interface to Core Network and Bearer information TLV object havinga highest priority.
 2. Multimedia Messaging Service capable mobileequipment according to claim 1, wherein the TLV object with the highestpriority is of mandatory status.
 3. Multimedia Messaging Service capablemobile equipment according to claim 1, comprising a storage medium onwhich the elementary file for Multimedia Messaging ConnectivityParameters is stored.
 4. Multimedia Messaging Service capable mobileequipment according to claim 3, wherein the storage medium includes asmart cardselected from a set of smart cards including a UMTS subscriberidentity module (USIM), SIM, WIM, R-UIM, and DIM.
 5. MultimediaMessaging Service capable mobile equipment according to claim 4, whereinthe UMTS subscriber identity module is on a Universal Integrated CircuitCard (UICC).
 6. Multimedia Messaging Service capable mobile equipmentaccording to claim 5, wherein the mobile equipment is user equipmentplugged into a UICC.
 7. Multimedia Messaging Service capable mobileequipment according to claim 1, wherein a plurality of MultimediaMessaging Connectivity Parameters are stored in the elementary file. 8.Multimedia Messaging Service capable mobile equipment according to claim7, wherein the plurality Multimedia Messaging Connectivity Parameterscontain one Interface to Core Network and Bearer information TLV object.9. Multimedia Messaging Service capable mobile equipment according toclaim 8, wherein an order of the MMS Connectivity TLV objects on a levelof a UMTS subscriber identity module define a priority of the Interfaceto Core Network and Bearer information, with the Interface to CoreNetwork and Bearer information TLV object in the first MMS ConnectivityTLV object having the highest priority.
 10. Method for selection of abearer, wherein a Multimedia Messaging Service capable mobile equipmentaccording to claim 1 automatically selects the bearer which is describedby the Interface to Core Network and Bearer information stored in theInterface to Core Network and Bearer information TLV object with thehighest priority.
 11. Method according to claim 10, wherein a userselects a preferred bearer manually if the bearer is not selectedautomatically.
 12. Method for selection of a bearer, wherein aMultimedia Messaging Service capable mobile equipment according to claim1 automatically selects the bearer which is described by the Interfaceto Core Network and Bearer information stored in the Interface to CoreNetwork and Bearer information TLV object with the highest priority. 13.Method for selection of a bearer, wherein a Multimedia Messaging Servicecapable mobile equipment according to claim 3 automatically selects thebearer which is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 14. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 4 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 15. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 5 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 16. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 6 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 17. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 7 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 18. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 9 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.
 19. Method forselection of a bearer, wherein a Multimedia Messaging Service capablemobile equipment according to claim 9 automatically selects the bearerwhich is described by the Interface to Core Network and Bearerinformation stored in the Interface to Core Network and Bearerinformation TLV object with the highest priority.